BMAD v6 Installation Update: Modularization + AgentVibes “talking” dev experience
The core changes in v6 are a rebuilt directory/artifact system plus voice (AgentVibes) formally integrated into the BMAD workflow.
1) Bottom line first: the two most tangible changes from v4 to v6
Section titled “1) Bottom line first: the two most tangible changes from v4 to v6”Change A: the directory moved from “single core” to an engineering structure of “Core + Modules + Manifests.”
In the v4 user guide, personalization preferences (tech stack, naming rules, etc.) were managed at .bmad-core/data/technical-preferences.md.
In v6 (Alpha), the official positioning is “Agent-as-Code + reproducible pipelines,” with an explicit workspace anatomy: .bmad/ stores profiles/blueprints/runs and other traceable artifacts.
Change B: AgentVibes is treated as the first-party experience layer: letting BMAD agents speak in Claude Code, switch voices, and be controlled by slash commands / MCP. AgentVibes’ official description is blunt: it was originally built to “add voice” to Claude Code and offers both MCP (natural-language control) and slash commands.
2) Directory structure: v4 “.bmad-core” vs v6 “.bmad + modules + artifacts”
Section titled “2) Directory structure: v4 “.bmad-core” vs v6 “.bmad + modules + artifacts””Breaking it down based on the installation log
v4 (common mental model for users)
Section titled “v4 (common mental model for users)”- Core directory:
.bmad-core/Stores preferences, data, templates; for example, the v4 user guide clearly points to.bmad-core/data/technical-preferences.mdfor preferences. - Web bundle workflow:
dist/teams/...The typical move is to copydist/teams/team-fullstack.txtinto a web UI/Claude/GPT as a “team prompt.” - Feels like a “prompt framework + directory convention.” Engineering-wise it works, but “traceable/reproducible outputs” were not the primary goal.
v6 (what your installation shows)
Section titled “v6 (what your installation shows)”From the log, the most important “on-disk” changes are:
- Root directory unified at
<project>/.bmad(yours:/Users/vsai/.../vs-ai-agents/.bmad) - Modular installation: Core + bmb + bmgd + bmm + cis
- Core: installs core agents (e.g.,
bmad-master.md) - bmb: Builder/Factory (the “factory” for custom agents, workflows, modules)
- bmm: Method (Analyst/PM/Dev/SM/UX, the full team)
- bmgd: Game Dev (and vendors cross-module workflows)
- cis: Creative Innovation Suite
- Core: installs core agents (e.g.,
At the same time, it makes a few things explicit that weren’t very visible in v4:
- Compiles/generates artifacts (manifests): the log literally reports “61 workflows, 21 agents, 5 tasks, 1 tools…” — evidence that v6 is leaning into “versionable/traceable” outputs (much more engineered). That matches the v6 Alpha emphasis on “reproducible, auditable, diffable.”
- Sprint artifact directory becomes an installation-time setting: you chose
docs/sprint-artifacts, and the installer created it (handy for teams running agile). - Custom extension directories are explicitly separated
bmad-custom-src: custom agents/workflowsbmad-custom-modules-src: custom modules
This essentially forces separation of “official modules” and “custom assets” for easier upgrades/merges.
- Sidecar memory directory: the log also replaced
{agent_sidecar_folder}→{project-root}/.bmad-user-memory(typically for agent “sidecar memory/run traces,” aligning with v6’s artifact-centric approach).
v4 is more “prompt framework + directory convention”; v6 is more “agent engineering system with build artifacts and traceable assets.”
3) AgentVibes integration: the key upgrades from “usable” to “pleasant”
Section titled “3) AgentVibes integration: the key upgrades from “usable” to “pleasant””The most attention-grabbing part of the log is this:
- Installer showed “AgentVibes TTS Injection Summary”
- Injected TTS into
.../.bmad/core/agents/bmad-master.md - Backups stored at
~/.bmad-tts-backups/ - Then launched the AgentVibes installer, dropping slash commands, TTS hooks, personality templates, background music, etc., into the project’s
.claude/
This matches AgentVibes’ official description closely:
What problem does AgentVibes solve?
Section titled “What problem does AgentVibes solve?”- It provides MCP (natural-language control): assistants don’t have to memorize slash commands; you can just say “switch to the Aria voice.”
- It also provides slash commands (zero token cost) like
/agent-vibes:list,/agent-vibes:switch Aria. - Multi–TTS-provider abstraction: Piper, macOS Say, ElevenLabs are all supported in the same capability layer (your log shows the macOS Say fast-install path).
- The installer explicitly states it will put commands/hooks/personalities/plugins into
.claude/.
Why does this matter for BMAD v6?
Section titled “Why does this matter for BMAD v6?”Because v6 targets “multi-agent, multi-workflow, multi-artifact,” humans’ attention gets fragmented across lots of process info. TTS brings two benefits:
- Stronger state feedback: start/finish cues are audible — no need to stare at the screen.
- Stronger sense of roles: switching PM/SM/Architect/Dev roles feels more like a team (AgentVibes’ BMAD integration highlights this).
4) Summary for moving from v4 to v6
Section titled “4) Summary for moving from v4 to v6”-
Plan how to migrate v4 preferences v4 preferences live at
.bmad-core/data/technical-preferences.md. v6 emphasizes workspace + policies + manifests (the structure under.bmad/). Recommendation: keep the v4 preference content as “team conventions,” then gradually map it to v6’s profile/policy system (avoid a one-shot forced migration that loses meaning). -
Put “custom assets” into the two directories you’ve configured
- agents/workflows →
bmad-custom-src - modules →
bmad-custom-modules-src
This reduces conflicts when upgrading v6 alpha/beta later.
- Default to “slash commands first” for AgentVibes AgentVibes also notes: MCP is convenient but consumes context tokens; slash commands are cheaper. In other words: use /-commands for daily work, then fall back to natural-language MCP occasionally for a balanced experience and cost.
Detailed log
Section titled “Detailed log”bunx bmad-method@alpha install
██████╗ ███╗ ███╗ █████╗ ██████╗ ™ ██╔══██╗████╗ ████║██╔══██╗██╔══██╗ ██████╔╝██╔████╔██║███████║██║ ██║ ██╔══██╗██║╚██╔╝██║██╔══██║██║ ██║ ██████╔╝██║ ╚═╝ ██║██║ ██║██████╔╝ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝ Build More, Architect Dreams v6.0.0-alpha.16
════════════════════════════════════════════════════════════════════════════════ BMAD™ Setup Build More, Architect Dreams v6.0.0-alpha.16════════════════════════════════════════════════════════════════════════════════
? Installation directory: /Users/vsai/WorkSpaces/vs/vs-ai-agents
Resolved installation path: /Users/vsai/WorkSpaces/vs/vs-ai-agentsDirectory exists and contains 1 item(s)? Install to this directory? Yes
────────────────────────────────────────────────────────────────────────────────BMAD™ Core ConfigurationConfigure the core settings for your BMAD™ installation.These settings will be used across all modules and agents.────────────────────────────────────────────────────────────────────────────────
██████╗ ███╗ ███╗ █████╗ ██████╗ ™ ██╔══██╗████╗ ████║██╔══██╗██╔══██╗ ██████╔╝██╔████╔██║███████║██║ ██║ ██╔══██╗██║╚██╔╝██║██╔══██║██║ ██║ ██████╔╝██║ ╚═╝ ██║██║ ██║██████╔╝ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝ Build More, Architect Dreams v6.0.0-alpha.16
════════════════════════════════════════════════════════════════════════════════ BMAD™ Installation Version 6.0.0-alpha.16════════════════════════════════════════════════════════════════════════════════
────────────────────────────────────────────────────────────────────────────────BMad Optimized Builder (BoMB) Module ConfigurationConfigure the settings for the BoMB Factory!The agent, workflow and module builder for BMAD™────────────────────────────────────────────────────────────────────────────────
? Where do custom agents and workflows get stored? bmad-custom-src? Where do custom modules get stored? bmad-custom-modules-src
────────────────────────────────────────────────────────────────────────────────BMad Game Development ModuleConfigure the settings for the BMad Game Development module────────────────────────────────────────────────────────────────────────────────
? What is the name of your game project? vs-ai-agents? Where should Sprint Artifacts be stored (stories, epics, temp context, etc...)? docs/sprint-artifacts? What is your game development experience level? Expert - Experienced game developer, be direct and technical? Which game development framework or engine do you want to install support for? Unity, Unreal Engine, Godot, Custom / Other
────────────────────────────────────────────────────────────────────────────────BMad Method™: Breakthrough Method of Agile-Ai Driven-DevAgent and Workflow Configuration for this module────────────────────────────────────────────────────────────────────────────────
? What is the title of your project you will be working on? vs-ai-agents? What is your technical experience level?This affects how agents explain concepts to you (NOT document content).Documents are always concise for LLM efficiency. Expert - Deep technical knowledge, be direct and technical? Where should Sprint Artifacts be stored (sprint status, stories, story context, temp context, etc...)? docs/sprint-artifacts? Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)? You have to setup your MCPs yourself; refer totest-architecture.md for hints. Yes? Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?This adds fixture-based utilities for auth, API requests, network recording, polling, intercept, recurse, logging, file download handling,and burn-in.You must install packages yourself, or use test architect's *framework command. Yes
────────────────────────────────────────────────────────────────────────────────Creative Innovation Suite (CIS) ModuleNo Configuration needed - uses Core Config only.────────────────────────────────────────────────────────────────────────────────
Configuring claude-code...
Configuring codex...? Where would you like to install Codex CLI prompts? Project-specific - Recommended for real work (requires CODEX_HOME=<project-dir>/.codex)
══════════════════════════════════════════════════════════════════════ Project-Specific Codex Configuration══════════════════════════════════════════════════════════════════════
Prompts will be installed to: <project>/.codex/prompts
⚠️ REQUIRED: You must set CODEX_HOME to use these prompts
Add this alias to your ~/.bashrc or ~/.zshrc:
alias codex='CODEX_HOME="$PWD/.codex" codex'
After adding, run: source ~/.bashrc (or source ~/.zshrc) (The $PWD uses your current working directory)
This tells Codex CLI to use prompts from this project instead of ~/.codex
══════════════════════════════════════════════════════════════════════
? Proceed with this installation option? No
Let's choose a different installation option.
? Where would you like to install Codex CLI prompts? Global - Simple for single project (~/.codex/prompts, but references THIS project only)
══════════════════════════════════════════════════════════════════════ IMPORTANT: Codex Configuration══════════════════════════════════════════════════════════════════════
/prompts installed globally to your HOME DIRECTORY.
⚠️ These prompts reference a specific .bmad path To use with other projects, you'd need to copy the .bmad dir
✓ You can now use /commands in Codex CLI Example: /bmad-bmm-agents-pm Type / to see all available commands
══════════════════════════════════════════════════════════════════════
? Proceed with this installation option? No
Let's choose a different installation option.
? Where would you like to install Codex CLI prompts? Project-specific - Recommended for real work (requires CODEX_HOME=<project-dir>/.codex)
══════════════════════════════════════════════════════════════════════ Project-Specific Codex Configuration══════════════════════════════════════════════════════════════════════
Prompts will be installed to: <project>/.codex/prompts
⚠️ REQUIRED: You must set CODEX_HOME to use these prompts
Add this alias to your ~/.bashrc or ~/.zshrc:
alias codex='CODEX_HOME="$PWD/.codex" codex'
After adding, run: source ~/.bashrc (or source ~/.zshrc) (The $PWD uses your current working directory)
This tells Codex CLI to use prompts from this project instead of ~/.codex
══════════════════════════════════════════════════════════════════════
? Proceed with this installation option? Yes⠋ Continuing installation... Created customize: core-bmad-master.customize.yaml Built agent: bmad-master.md✔ Core installed✔ Dependencies resolved⠋ Installing module: bmb... Created customize: bmb-bmad-builder.customize.yaml Compiled agent: bmad-builder -> agents/bmad-builder.md✔ Module installed: bmb⠋ Installing module: bmgd... Vendoring cross-module workflows for bmgd... Processing: game-architect.agent.yaml Vendoring: bmm/workflows/4-implementation/correct-course → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Processing: game-dev.agent.yaml Vendoring: bmm/workflows/4-implementation/dev-story → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Vendoring: bmm/workflows/4-implementation/code-review → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Source workflow not found: /private/tmp/bunx-501-bmad-method@alpha/node_modules/bmad-method/src/modules/bmm/workflows/4-implementation/story-done Processing: game-scrum-master.agent.yaml Vendoring: bmm/workflows/4-implementation/sprint-planning → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Source workflow not found: /private/tmp/bunx-501-bmad-method@alpha/node_modules/bmad-method/src/modules/bmm/workflows/4-implementation/epic-tech-context Vendoring: bmm/workflows/4-implementation/create-story → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Source workflow not found: /private/tmp/bunx-501-bmad-method@alpha/node_modules/bmad-method/src/modules/bmm/workflows/4-implementation/story-context Source workflow not found: /private/tmp/bunx-501-bmad-method@alpha/node_modules/bmad-method/src/modules/bmm/workflows/4-implementation/story-ready Vendoring: bmm/workflows/4-implementation/retrospective → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml Vendoring: bmm/workflows/4-implementation/correct-course → bmgd/workflows/bmgd Updated config_source to: .bmad/bmgd/config.yaml ✓ Workflow vendoring complete
Created customize: bmgd-game-architect.customize.yaml Compiled agent: game-architect -> agents/game-architect.md Created customize: bmgd-game-designer.customize.yaml Compiled agent: game-designer -> agents/game-designer.md Created customize: bmgd-game-dev.customize.yaml Compiled agent: game-dev -> agents/game-dev.md Created customize: bmgd-game-scrum-master.customize.yaml Compiled agent: game-scrum-master -> agents/game-scrum-master.md✔ Module installed: bmgd⠙ Installing module: bmm... Created customize: bmm-analyst.customize.yaml Compiled agent: analyst -> agents/analyst.md Created customize: bmm-architect.customize.yaml Compiled agent: architect -> agents/architect.md Created customize: bmm-dev.customize.yaml Compiled agent: dev -> agents/dev.md Created customize: bmm-pm.customize.yaml Compiled agent: pm -> agents/pm.md Created customize: bmm-quick-flow-solo-dev.customize.yaml Compiled agent: quick-flow-solo-dev -> agents/quick-flow-solo-dev.md Created customize: bmm-sm.customize.yaml Compiled agent: sm -> agents/sm.md Created customize: bmm-tea.customize.yaml Compiled agent: tea -> agents/tea.md Created customize: bmm-tech-writer.customize.yaml Compiled agent: tech-writer -> agents/tech-writer.md Created customize: bmm-ux-designer.customize.yaml Compiled agent: ux-designer -> agents/ux-designer.md✔ Module installed: bmm⠋ Installing module: cis... Created customize: cis-brainstorming-coach.customize.yaml Compiled agent: brainstorming-coach -> agents/brainstorming-coach.md Created customize: cis-creative-problem-solver.customize.yaml Compiled agent: creative-problem-solver -> agents/creative-problem-solver.md Created customize: cis-design-thinking-coach.customize.yaml Compiled agent: design-thinking-coach -> agents/design-thinking-coach.md Created customize: cis-innovation-strategist.customize.yaml Compiled agent: innovation-strategist -> agents/innovation-strategist.md Created customize: cis-presentation-master.customize.yaml Compiled agent: presentation-master -> agents/presentation-master.md Created customize: cis-storyteller.customize.yaml Compiled agent: storyteller -> agents/storyteller.md✔ Module installed: cis✔ Module configurations generated✔ Manifests generated: 61 workflows, 21 agents, 5 tasks, 1 tools, 88 files✔ Configured 18 IDEs✔ IDE documentation copied⠋ Running module-specific installers...🏗️ Installing Core Module...Configuring Core for IDEs: claude-code, codex, cursor, github-copilot, antigravity, opencode, windsurf, rovo-dev, auggie, cline, crush, gemini, iflow, kilo, kiro-cli, qwen, roo, trae✓ Core Module installation complete🔧 Setting up BMB Module... Setting up custom agents at: /Users/vsai/WorkSpaces/vs/vs-ai-agents/bmad-custom-src ✓ Created custom.yaml at /Users/vsai/WorkSpaces/vs/vs-ai-agents/bmad-custom-src/custom.yaml Setting up custom modules at: /Users/vsai/WorkSpaces/vs/vs-ai-agents/bmad-custom-modules-src ✓ Created modules directory at /Users/vsai/WorkSpaces/vs/vs-ai-agents/bmad-custom-modules-src Configuring BMB for IDEs: claude-code, codex, cursor, github-copilot, antigravity, opencode, windsurf, rovo-dev, auggie, cline, crush, gemini, iflow, kilo, kiro-cli, qwen, roo, trae✓ BMB Module setup complete🚀 Installing BMM Module...Creating story directory: docs/sprint-artifactsConfiguring BMM for IDEs: claude-code, codex, cursor, github-copilot, antigravity, opencode, windsurf, rovo-dev, auggie, cline, crush, gemini, iflow, kilo, kiro-cli, qwen, roo, trae BMM-Claude Code Specifics installed No BMM-specific configuration for Codex No BMM-specific configuration for Cursor No BMM-specific configuration for GitHub Copilot No BMM-specific configuration for Google Antigravity No BMM-specific configuration for OpenCode BMM-Windsurf Specifics installed Warning: Unknown platform code 'rovo-dev'. Skipping BMM configuration. No BMM-specific configuration for Auggie No BMM-specific configuration for Cline No BMM-specific configuration for Crush No BMM-specific configuration for Gemini CLI No BMM-specific configuration for iFlow No BMM-specific configuration for KiloCoder Warning: Unknown platform code 'kiro-cli'. Skipping BMM configuration. No BMM-specific configuration for QwenCoder No BMM-specific configuration for Roo Cline No BMM-specific configuration for Trae✓ BMM Module installation complete🎨 Installing CIS Module...Configuring CIS for IDEs: claude-code, codex, cursor, github-copilot, antigravity, opencode, windsurf, rovo-dev, auggie, cline, crush, gemini, iflow, kilo, kiro-cli, qwen, roo, trae✓ CIS Module installation complete✔ Module-specific installers completed
Configuring agent sidecar folders...
Replacing {agent_sidecar_folder} with: {project-root}/.bmad-user-memory ✓ Replaced 1 occurrence(s) in bmb/workflows/create-module/templates/agent.template.md ✓ Replaced 1 occurrence(s) in bmb/docs/agents/expert-agent-architecture.md ✓ Replaced 4 occurrence(s) in bmb/docs/agents/agent-menu-patterns.md ✓ Updated 3 agent file(s) with 6 sidecar reference(s)
════════════════════════════════════════════════════════════════════════════════ Installation Complete BMAD™ has been successfully installed════════════════════════════════════════════════════════════════════════════════
╭──────────────────────────────────────────────────────────────────────────────╮ │ │ │ 📁 Installation Path: │ │ /Users/vsai/WorkSpaces/vs/vs-ai-agents/.bmad │ │ │ │ 📦 Modules Installed: bmb, bmgd, bmm, cis │ │ │ │ 🔧 Tools Configured: claude-code, codex, cursor, github-copilot, │ │ antigravity, opencode, windsurf, rovo-dev, auggie, cline, crush, gemini, │ │ iflow, kilo, kiro-cli, qwen, roo, trae │ │ │ │ 🎤 AgentVibes TTS: Enabled │ │ │ ╰──────────────────────────────────────────────────────────────────────────────╯
═══════════════════════════════════════════════════ AgentVibes TTS Injection Summary═══════════════════════════════════════════════════
What is TTS Injection?
TTS (Text-to-Speech) injection adds voice instructions to BMAD agents, enabling them to speak their responses aloud using AgentVibes.
Example: When you activate the PM agent, it will greet you with spoken audio like "Hey! I'm your Project Manager. How can I help?"
✅ TTS injection applied to 1 file(s):
Agent TTS (individual agent voices): • /Users/vsai/WorkSpaces/vs/vs-ai-agents/.bmad/core/agents/bmad-master.md
Backups & Recovery:
Pre-injection backups are stored in: ~/.bmad-tts-backups/
To restore original files (removes TTS instructions): bmad-tts-injector.sh --restore /Users/vsai/WorkSpaces/vs/vs-ai-agents/.bmad
💡 BMAD agents will now speak when activated! Ensure AgentVibes is installed: https://agentvibes.org
✨ BMAD is ready to use!
✨ Installation complete!BMAD Core and Selected Modules have been installed to: /Users/vsai/WorkSpaces/vs/vs-ai-agents/.bmad
Thank you for helping test the early release version of the new BMad Core and BMad Method!Stable Beta coming soon - please read the full README.md and linked documentation to get started!
🎙️ AgentVibes TTS SetupAgentVibes provides voice synthesis for BMAD agents with: • ElevenLabs AI (150+ premium voices) • Piper TTS (50+ free voices)
Press Enter to start AgentVibes installer...
Need to install the following packages:agentvibes@2.17.4Ok to proceed? (y) y
╭──────────────────────────────────────────────────────────────────────────────╮│ Agent Vibes v2.17.4 Installer • Page 5/15 ││ ││ Installation Confirmation ││ ││ https://agentvibes.org • https://github.com/paulpreibisch/AgentVibes │╰──────────────────────────────────────────────────────────────────────────────╯
Play audio welcome message from Paul, creator of AgentVibes.
✔ 🎵 Listen to Welcome Message? Yes⠋ Playing welcome message... (Welcome demo skipped - audio file not found)✔ Welcome message complete!✔✅ Ready to install AgentVibes with macOS Say? Yes
✔ .claude directory found! Location: /Users/vsai/WorkSpaces/vs/vs-ai-agents/.claude
✔ Installed 34 slash commands!
✔ Installed TTS scripts!
✔ Installed personality templates!
ℹ No plugin files found (optional)
ℹ No BMAD config files found (optional)
✔ Installed 16 background music tracks!
✔ Installed 6 config files!
✓ audio-effects.cfg╭──────────────────────────────────────────────────────────────────────────────╮│ Agent Vibes v2.17.4 Installer • Page 6/11 ││ ││ Summary: Slash Commands ││ ││ https://agentvibes.org • https://github.com/paulpreibisch/AgentVibes │╰──────────────────────────────────────────────────────────────────────────────╯
╭──────────────────────────────────────────────────────────────────────────────╮│ Agent Vibes v2.17.4 Installer • Page 7/11 ││ ││ Summary: Background Music ││ ││ https://agentvibes.org • https://github.com/paulpreibisch/AgentVibes │╰──────────────────────────────────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────── 🎵 Background Music ────────────────────────────────────────────────────────╮ │ │ │ 16 Background Music Tracks Installed │ │ │ │ Agents need to have fun too! 🎉 Spice things up with background music. │ │ │ │ 💡 How to control background music: │ │ │ │ Slash Commands: │ │ /agent-vibes:background-music on - Enable music │ │ /agent-vibes:background-music off - Disable music │ │ /agent-vibes:background-music set chillwave - Change track │╭──────────────────────────────────────────────────────────────────────────────╮│ Agent Vibes v2.17.4 Installer • Page 8/11 ││ ││ Summary: TTS Scripts ││ ││ https://agentvibes.org • https://github.com/paulpreibisch/AgentVibes │╰──────────────────────────────────────────────────────────────────────────────╯
╭────────────────────────── 🔧 TTS Scripts ──────────────────────────╮ │ │ │ 37 TTS Hook Scripts Installed │
✅ AgentVibes is Ready!
Launch Claude Code with MCP: claude --mcp-config .mcp.json
• /agent-vibes:list - See all available voices • /agent-vibes:switch <name> - Change your voice • /agent-vibes:personality <style> - Set personality
✓ AgentVibes installation complete
